Skip to content

chore(release): 5.2.7 — consolidate PRs #744-#750 from 5.2.6 - #751

Merged
rafaelscosta merged 2 commits into
mainfrom
chore/release-5.2.7
May 18, 2026
Merged

chore(release): 5.2.7 — consolidate PRs #744-#750 from 5.2.6#751
rafaelscosta merged 2 commits into
mainfrom
chore/release-5.2.7

Conversation

@rafaelscosta

@rafaelscosta rafaelscosta commented May 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

Consolidates 7 PRs merged after the 5.2.6 release into a single npm publish. None of them required an immediate hotfix on their own, but together they unblock cohort students from a real CI/CD failure mode (#739 Bug 1) and remove three sources of registry drift.

What ships in 5.2.7

PR Commit Scope
#744 66b302a Pipeline hardening + canonical release-procedure.md SOP
#745 342ef63 Ecosystem alignment: Issue 10 troubleshooting + slim task wrappers
#746 ef7a352 Internal package.json rebrand + namespace drift gate (#739 Bug 2)
#747 e5cd355 70 legacy path refs aligned with .aiox-core layout (closes #741)
#748 1f97f6f IDS extractPurpose priority chain + syncSelfRegistryEntry
#749 70fa5e2 IDS looksLikePlaceholder filter (16 garbage purposes removed)
#750 21782cc Installer honors --ci/--yes at CLAUDE.md merge prompt (closes #739 Bug 1)

Version sites bumped (5 — up from 4)

The previous SOP listed 4 sites. PR #746 added validate-aiox-core-namespace.js (rule 4 requires .aiox-core/package.json version to match root). This release codifies the 5th site as mandatory.

  • package.json (root): 5.2.6 → 5.2.7
  • compat/aiox-core/package.json: version + dep["@aiox-squads/core"] → 5.2.7
  • packages/installer/package.json: 3.3.5 → 3.3.6 (fix(installer): honor --ci/--yes at CLAUDE.md merge prompt (closes #739 Bug 1) #750 touched installer src)
  • .aiox-core/package.json (internal): 5.2.6 → 5.2.7
  • package-lock.json: refreshed
  • CHANGELOG.md: new [5.2.7] entry
  • docs/guides/release-procedure.md: bumped "4 sites" rule to "5 sites"

Validation (local)

  • npm run lint → exit 0
  • npm run test:ci → 8510 passed (151 skipped), 344/355 suites, 229s
  • npx jest tests/installer/ --no-coverage → 276/276 pass
  • npm run validate:publish → PASS (12911 files; namespace sync verified)
  • Working tree clean post-commit (only pro submodule drift, deliberately not included)
  • IDS-Hook regen of entity-registry.yaml + install-manifest.yaml included in the commit (per SOP)

Post-merge plan

Tag v5.2.7 annotated against origin/main, push tag → npm-publish.yml workflow disparado. publish job é hard fail; publish_workspace_packages (installer 3.3.6), publish_legacy_aiox_core (aiox-core compat 5.2.7), smoke_test_exports, notify são advisory per SOP.

Test plan

  • CI essentials green (Test, Installer Smoke Matrix, ESLint, TypeScript, CodeQL)
  • Bypass dance (ruleset 13330052 + legacy branch protection) atomic with trap EXIT restore
  • npm view @aiox-squads/core version → 5.2.7 with latest dist-tag
  • E2E install in /tmp/aiox-e2e/scenario (worst-case workspace ancestor topology)

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Summary by CodeRabbit

  • Bug Fixes

    • Installer and IDS compatibility fixes, improved non-interactive prompt handling, and prevention of invalid placeholder entries reaching the entity registry.
  • Documentation

    • Expanded release procedure guidance and added changelog formatting updates and wrapper/task documentation.
  • Chores

    • Released core packages (5.2.7) and installer (3.3.6); refreshed release metadata and integrity hashes; added namespace/version validation as part of publish checks.

Review Change Stack

Consolidates 7 PRs merged after the 5.2.6 release. None of them
required an immediate hotfix on their own, but together they unblock
cohort students from a real CI/CD failure mode (#739 Bug 1) and
remove three sources of registry drift.

## What ships in 5.2.7

- **#744** (66b302a) — Pipeline hardening: `publish_legacy_aiox_core` race fix,
  smoke timeout 90s→240s with dual visibility check, structured notify summary,
  Windows path escape fix via WORKSPACE_DIR env var. Plus the canonical
  `docs/guides/release-procedure.md` SOP.
- **#745** (342ef63) — Ecosystem alignment: `installation-troubleshooting.md`
  Issue 10 (install-side recovery for the npm-hijack symptom), aiox-pro-access.md
  link, slim wrappers for publish-npm.md/release-management.md tasks pointing
  at the SOP, devops.md Release Procedure section.
- **#746** (ef7a352) — Internal `.aiox-core/package.json` rebranded
  `@aiox-fullstack/core@4.31.1` → `@aiox-squads/core-internal@5.2.7` (private,
  no phantom peerDeps). New `scripts/validate-aiox-core-namespace.js` (5-rule
  gate) wired into `validate:publish`. Closes #739 Bug 2.
- **#747** (e5cd355) — 70 substitutions across 17 files realigning legacy
  `aiox-core/{templates,checklists,agents,tasks,workflows,agent-teams}/<X>`
  references to current `.aiox-core/...` layout. Unblocks
  `@po *validate-story-draft`. Closes #741.
- **#748** (1f97f6f) — IDS `extractPurpose()` rewritten as strict priority
  chain (frontmatter → ## Purpose → ## Overview → # Title → fallback).
  Removed body-level regex that picked up example transcripts as
  purposes. New `syncSelfRegistryEntry()` writes sentinel
  `sha256:<self-reference>` checksum for the registry's own record.
- **#749** (70fa5e2) — `looksLikePlaceholder()` filter excludes 16 garbage
  purposes (`{Brief...}`, `{{TASK_TITLE}}`, `${context.componentName}`).
- **#750** (21782cc) — Installer honors `--ci` / `--yes` / `--skipPrompts`
  flags at the CLAUDE.md merge prompt. Non-interactive runs no longer block
  waiting for keyboard input. Closes #739 Bug 1.

## Version sites bumped (5 — up from 4 in the previous SOP)

- `package.json` (root): 5.2.6 → 5.2.7
- `compat/aiox-core/package.json`: version + dep["@aiox-squads/core"] 5.2.6 → 5.2.7
- `packages/installer/package.json`: 3.3.5 → 3.3.6 (#750 touched installer src)
- `.aiox-core/package.json` (internal): 5.2.6 → 5.2.7 (validate-aiox-core-namespace
  enforces lockstep with root — new in 5.2.7, first release under the gate)
- `package-lock.json` refresh
- `CHANGELOG.md`: new [5.2.7] entry
- `docs/guides/release-procedure.md`: bump the "4 sites" rule to "5 sites"
  reflecting the validate-aiox-core-namespace gate added in PR #746

## Validation

- `npm run lint` → exit 0
- `npm run test:ci` → 8510 passed (151 skipped), 344/355 suites, 229s
- `npx jest tests/installer/ --no-coverage` → 276/276 pass
- `npm run validate:publish` → PASS (12911 files; namespace sync verified)

Pro install hijack fix (#742) shipped in 5.2.6 and remains in production —
this release does not re-iterate it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented May 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
aiox-core Ready Ready Preview, Comment May 18, 2026 4:28am

Request Review

@github-actions github-actions Bot added area: installer Installer and setup (packages/installer/) area: docs Documentation (docs/) labels May 18, 2026
@coderabbitai

coderabbitai Bot commented May 18, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7b2c091f-348a-44de-8001-5005fab91275

📥 Commits

Reviewing files that changed from the base of the PR and between 6c0ad2b and 192514e.

📒 Files selected for processing (1)
  • docs/guides/release-procedure.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/guides/release-procedure.md

Walkthrough

Coordinated release updates: bump root and internal packages to 5.2.7, refresh .aiox-core/install-manifest.yaml metadata and integrity hashes, align compat wrapper, update CHANGELOG and release-procedure SOP for five-location version lockstep, and bump installer to 3.3.6.

Changes

Release 5.2.7 Version Coordination

Layer / File(s) Summary
Core and root package bump with manifest regeneration
package.json, .aiox-core/package.json, .aiox-core/install-manifest.yaml
Root and internal packages bumped to 5.2.7; .aiox-core/install-manifest.yaml version and generated_at updated; SHA256 hashes for data/entity-registry.yaml and package.json regenerated.
Compatibility wrapper version and dependency alignment
compat/aiox-core/package.json
compat/aiox-core version set to 5.2.7 and its @aiox-squads/core dependency aligned to 5.2.7.
Changelog and release-procedure SOP updates
CHANGELOG.md, docs/guides/release-procedure.md
Added 5.2.7 changelog entry and updated release-procedure to require five-version bump sites and expanded CHANGELOG template (adds ### Changed).
Installer package version bump
packages/installer/package.json
Installer package version incremented from 3.3.5 to 3.3.6.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

area: devops, area: core, area: workflows

Suggested reviewers

  • Pedrovaleriolopez
  • oalanicolas
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically summarizes the main change: a version bump consolidating multiple PRs into release 5.2.7, which is directly reflected in the changeset updates to manifests, changelog, and documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-5.2.7

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented May 18, 2026

Copy link
Copy Markdown
Contributor

📊 Coverage Report

Coverage report not available

📈 Full coverage report available in Codecov


Generated by PR Automation (Story 6.1)

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
docs/guides/release-procedure.md (1)

36-38: ⚡ Quick win

Clarify “lockstep” wording to avoid accidental installer over-bumps.

Line 36 currently implies all five versions must match numerically, but Line 44 explicitly treats packages/installer/package.json as conditional. Rewording this line will prevent release-operator confusion.

✏️ Proposed wording tweak
-Bump **all five** version sites in lockstep. Mismatches cause silent publish
-failures that only show up in the smoke tests OR are caught by
-`validate-aiox-core-namespace.js` (which is wired into `validate:publish`).
+Review **all five** version sites during release prep. Root/core-internal/compat
+must stay in lockstep where specified below; installer is bumped only when
+installer changes are included.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/guides/release-procedure.md` around lines 36 - 38, The sentence "Bump
**all five** version sites in lockstep." is ambiguous and can cause accidental
over-bumping of the installer; update the wording in the release-procedure
document to explicitly state that four core version locations must be kept in
sync and that packages/installer/package.json should only be bumped when the
installer release is required (i.e., treat packages/installer/package.json as
conditional), and mention validate-aiox-core-namespace.js (validate:publish) and
the smoke tests as the checks that will catch mismatches.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/guides/release-procedure.md`:
- Around line 36-38: The sentence "Bump **all five** version sites in lockstep."
is ambiguous and can cause accidental over-bumping of the installer; update the
wording in the release-procedure document to explicitly state that four core
version locations must be kept in sync and that packages/installer/package.json
should only be bumped when the installer release is required (i.e., treat
packages/installer/package.json as conditional), and mention
validate-aiox-core-namespace.js (validate:publish) and the smoke tests as the
checks that will catch mismatches.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a618c7c8-218c-49c6-85d6-96096fbf1a48

📥 Commits

Reviewing files that changed from the base of the PR and between 21782cc and 6c0ad2b.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (8)
  • .aiox-core/data/entity-registry.yaml
  • .aiox-core/install-manifest.yaml
  • .aiox-core/package.json
  • CHANGELOG.md
  • compat/aiox-core/package.json
  • docs/guides/release-procedure.md
  • package.json
  • packages/installer/package.json

coderabbitai[bot]
coderabbitai Bot previously approved these changes May 18, 2026
…ding

PR #751 CodeRabbit review flagged that the "Bump all five version sites in
lockstep" wording was ambiguous — the table below explicitly treats
`packages/installer/package.json` as conditional ("patch bump if installer
changed; otherwise leave"). Operators reading only line 36 could over-bump
the installer.

Reworded to distinguish:
- Root + internal manifest + compat: MUST stay in lockstep at same version
- packages/installer: bumped ONLY when installer source changed (not every release)

Also explicit on the two failure-mode detection layers:
- Smoke tests (catch silent publish mismatches)
- validate-aiox-core-namespace.js wired into validate:publish (rule 4 enforces lockstep)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rafaelscosta
rafaelscosta merged commit 536bda9 into main May 18, 2026
48 checks passed
@rafaelscosta
rafaelscosta deleted the chore/release-5.2.7 branch May 18, 2026 04:31
tuanmedeiros pushed a commit to tuanmedeiros/aios-core-synkraay that referenced this pull request Jun 2, 2026
…m 5.2.6 (SynkraAI#751)

* chore(release): bump to 5.2.7 — consolidate PRs SynkraAI#744-SynkraAI#750 from 5.2.6

Consolidates 7 PRs merged after the 5.2.6 release. None of them
required an immediate hotfix on their own, but together they unblock
cohort students from a real CI/CD failure mode (SynkraAI#739 Bug 1) and
remove three sources of registry drift.

## What ships in 5.2.7

- **SynkraAI#744** (d949918) — Pipeline hardening: `publish_legacy_aiox_core` race fix,
  smoke timeout 90s→240s with dual visibility check, structured notify summary,
  Windows path escape fix via WORKSPACE_DIR env var. Plus the canonical
  `docs/guides/release-procedure.md` SOP.
- **SynkraAI#745** (b728a39) — Ecosystem alignment: `installation-troubleshooting.md`
  Issue 10 (install-side recovery for the npm-hijack symptom), aiox-pro-access.md
  link, slim wrappers for publish-npm.md/release-management.md tasks pointing
  at the SOP, devops.md Release Procedure section.
- **SynkraAI#746** (dea939e) — Internal `.aiox-core/package.json` rebranded
  `@aiox-fullstack/core@4.31.1` → `@aiox-squads/core-internal@5.2.7` (private,
  no phantom peerDeps). New `scripts/validate-aiox-core-namespace.js` (5-rule
  gate) wired into `validate:publish`. Closes SynkraAI#739 Bug 2.
- **SynkraAI#747** (e874103) — 70 substitutions across 17 files realigning legacy
  `aiox-core/{templates,checklists,agents,tasks,workflows,agent-teams}/<X>`
  references to current `.aiox-core/...` layout. Unblocks
  `@po *validate-story-draft`. Closes SynkraAI#741.
- **SynkraAI#748** (e8f8761) — IDS `extractPurpose()` rewritten as strict priority
  chain (frontmatter → ## Purpose → ## Overview → # Title → fallback).
  Removed body-level regex that picked up example transcripts as
  purposes. New `syncSelfRegistryEntry()` writes sentinel
  `sha256:<self-reference>` checksum for the registry's own record.
- **SynkraAI#749** (6113083) — `looksLikePlaceholder()` filter excludes 16 garbage
  purposes (`{Brief...}`, `{{TASK_TITLE}}`, `${context.componentName}`).
- **SynkraAI#750** (1d16b51) — Installer honors `--ci` / `--yes` / `--skipPrompts`
  flags at the CLAUDE.md merge prompt. Non-interactive runs no longer block
  waiting for keyboard input. Closes SynkraAI#739 Bug 1.

## Version sites bumped (5 — up from 4 in the previous SOP)

- `package.json` (root): 5.2.6 → 5.2.7
- `compat/aiox-core/package.json`: version + dep["@aiox-squads/core"] 5.2.6 → 5.2.7
- `packages/installer/package.json`: 3.3.5 → 3.3.6 (SynkraAI#750 touched installer src)
- `.aiox-core/package.json` (internal): 5.2.6 → 5.2.7 (validate-aiox-core-namespace
  enforces lockstep with root — new in 5.2.7, first release under the gate)
- `package-lock.json` refresh
- `CHANGELOG.md`: new [5.2.7] entry
- `docs/guides/release-procedure.md`: bump the "4 sites" rule to "5 sites"
  reflecting the validate-aiox-core-namespace gate added in PR SynkraAI#746

## Validation

- `npm run lint` → exit 0
- `npm run test:ci` → 8510 passed (151 skipped), 344/355 suites, 229s
- `npx jest tests/installer/ --no-coverage` → 276/276 pass
- `npm run validate:publish` → PASS (12911 files; namespace sync verified)

Pro install hijack fix (SynkraAI#742) shipped in 5.2.6 and remains in production —
this release does not re-iterate it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: address CodeRabbit nitpick on release-procedure.md lockstep wording

PR SynkraAI#751 CodeRabbit review flagged that the "Bump all five version sites in
lockstep" wording was ambiguous — the table below explicitly treats
`packages/installer/package.json` as conditional ("patch bump if installer
changed; otherwise leave"). Operators reading only line 36 could over-bump
the installer.

Reworded to distinguish:
- Root + internal manifest + compat: MUST stay in lockstep at same version
- packages/installer: bumped ONLY when installer source changed (not every release)

Also explicit on the two failure-mode detection layers:
- Smoke tests (catch silent publish mismatches)
- validate-aiox-core-namespace.js wired into validate:publish (rule 4 enforces lockstep)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation (docs/) area: installer Installer and setup (packages/installer/)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Bug Report: Path Mismatch in AIOX Framework. [Bug]: --ci --yes ignorado no prompt de merge do CLAUDE.md durante install (v5.2.5)

1 participant